EDAT SOO_20230707.docx

SOO For USSOCOM

SOO For USSOCOM

STATEMENT OF OBJECTIVES (SOO)

FOR

United States Special Operations Command (USSOCOM) Enterprise Development, Applications, and Training (EDAT) 07 July 2023 Introduction Description of Services The objective is to provide IT Enterprise Development, Application and Training Support Services to encompass all United States Special Operations Command (USSOCOM), within the Continental United States (CONUS) and outside of the Continental United States (OCONUS).

USSOCOM Agency Mission The U.S. Special Operations Command (USSOCOM) is a combatant command with global presence, ready to defend the nation and to protect U.S. interests worldwide as part of the Joint Force. Conducting special operations effectively on a global scale requires the foremost enabler, the Special Operations Forces (SOF) Information Environment (SIE). The SIE includes the people. processes, and platforms that – in concert with our Joint Forces, Interagency and Multinational partners – sustains our national defense mission.

The focus of the USSOCOM CIO/J6 is SOF C5I organizations, working as one team, to rapidly develop and deploy innovative solutions on a resilient global network and connect highly mobile and capable SOF professionals to the information they need before they need it. At the heart of this team are the Active Duty, Government, and Contracted Civilians who comprise the leadership, engineering, design, programming, operations, and sustainment of the SIE. USSOCOM relies on this team 24/7 to plan, install, operate, and maintain an “always up” SIE.

Innovation is paramount as we focus on our pacing challenge and as competition in the gray-zone intensifies. We must adapt to emerging threats and demands to ensure we have the information and decision advantage in executing special operations activities in ways we have never seen before. Therefore, in our imperative to sustain SOF decision making globally, every teammate is critical in USSOCOM’s J6’s “all hands” mission to meet these Lines of Effort (LOE):

LOE 1: Develop People LOE 2: Resilient and Available Infrastructure LOE 3: Security from Enterprise to Edge LOE 4: Enable the Joint Fight LOE 5: Support the Warfighter for integrated defense, crises, and conflict Background USSOCOM develops and employs fully capable SOF to conduct global special operations and activities as part of the Joint Force to support persistent, networked, and distributed Combatant Command operations and campaigns against state and non-state actors to protect and advance U.S. policies and objectives. USSOCOM has evolved since its inception. Rather than a mere "break-glass-in-case-of-war" force, SOF are now proactively engaged across the "battle space" of the Geographic Combatant Commands, providing key integrating and enabling capabilities to support their campaigns and operations. SOF operate and fight in every corner of the world as an integrated joint, combined and interagency force. Today, there are approximately 56,000 active duty, 7,400 reserve, guard, and 6,600 civilian personnel across the SOF enterprise. Every day, USSOCOM sustains a deployed or forward stationed force of approximately 8,000 across 80 plus countries. They are conducting the entire range of SOF missions in both combat and noncombat situations with a variety of Joint, Interagency, International, and Multi-national partners.

Delivery Environment General The USSOCOM has a requirement to provide enterprise-wide information technology (IT) services and distribution to USSOCOM and its’ respective Components and Theater Special Operations Commands (TSOCs) through a modern, flexible, scalable, performance-based service management and delivery framework. The contract may be modified to add additional customers. The acronym USSOCOM, as used in this SOO, applies to all USSOCOM Headquarters organizations, Components, and TSOCs, as well as any future entity which USSOCOM may establish to support the Command’s mission. The potential customers for this contract are listed in Table 1.

Table 1. USSOCOM Commands and TSOCs.

The Enterprise Development, Application and Training (EDAT) service delivery environment is comprised of a series of interconnected IT systems whose purpose is the integration of information, applications and processes throughout USSOCOM’s global operations as well as across Department of Defense (DoD) organizational boundaries.

The acquisitions will contribute to enhancing USSOCOM’s ability to support the USSOCOM mission, as well as meet the net-centric DoD acquisition parameters. The acquisitions will also build on the existing foundation to increase operations efficiency, capabilities, and deliver flexibility through standardized and consistently applied policies, procedures, oversight, resource allocation, and the provision of value-added support. To achieve USSOCOM objectives and requirements, the delivery of IT services must be well-integrated, flexible, and adaptable across all IT service areas, with the ability to rapidly scale in response to USSOCOM’s dynamic mission. Requirements of this contract cross the service areas to provide USSOCOM organizations with an umbrella contract to support services at worldwide locations. USSOCOM participating entities require teams of highly-skilled personnel who can uphold a high level of performance across the IT services noted in Section 3. To ensure USSOCOM objectives are met, and emerging solutions are implemented into the SIE with the highest standards, the Government will initiate a project requirements document (PRD) which will kick off a collaborative effort between the Government and contractor to ensure mission needs are met. The collaborative vantage of the PRD will ensure that the Government and contractor are establishing pertinent new technology solutions at the TO level. The PRD will set a baseline of performance requirements which will reinforce at the TO level. The Enterprise Development, Application and Training services must integrate with Enterprise contractors and Enterprise USSOCOM processes; and readily support work requirements CONUS as well as remote/OCONUS locations, including theaters of active military operations.

Service Delivery Summary (SDS) The contractor(s) Service Delivery shall perform to the standards outlined in this basic contract Statement of Objectives (SOO) SDS as well as the specific requirements and standards outlined within each awarded TO. The contractor(s) shall ensure all services are provided efficiently and economically, while providing a quality product or quality service to meet participating entity requirements.

Roles and Responsibilities USSOCOM Information Technology Management Office (ITMO) ITMO will administer the transition, coordination, and ongoing management of all IT service areas to provide Enterprise-wide consistency and standardization. USSOCOM will manage contract, surveillance, and financial services.

Contracting Officer Representative (COR) The Contracting Officer Representative (COR) will ensure that the work under this contract is subject to the technical direction identified below or designated at the TO level. Technical direction must be within the scope of the specification(s)/work statement. Technical direction may be oral or in writing. Oral direction shall be confirmed by the COR in writing within 5 working days. The contractor shall proceed promptly with performance actions resulting from the technical direction issued by the COR. If, in the opinion of the contractor, any direction of the Contracting Officer (KO), COR or the KO’s designee, falls within the COR Limitations listed in section 5.1.2, the contractor shall immediately notify the KO no later than the beginning of the next Government workday. Failure of the contractor and the KO to agree that technical direction is within the scope of the contract shall be subject to the terms of FAR 52.233-1 “Disputes”.

Contractor Responsibilities Contractor(s) shall meet all requirements and responsibilities in support of USSOCOM as outlined in this SOO, including subsequent at the TO level. All support and staff shall be fully trained, professional, and customer oriented, consistently providing responsive, flexible, innovative, and cost-effective service. The contractor(s) shall ensure quality work performance in accordance with applicable standards and guidelines. The contractor(s) shall perform the requirements of this SOO in an environmentally acceptable and safe manner consistent with Federal, State and Local laws as well as applicable policies, regulations and instructions. The contractor(s) shall provide all personnel, supervision, and other items necessary to perform the services and provide support to all mission areas of USSOCOM as specified in this SOO and ordered under individual at the TO level. Performance of work under this contract is subject to the technical direction of the COR.

This SOO is meant as an overview of the basic scope of requirements; details will be provided for each individual requirement in subsequent TO.

Scope and Objectives The scope of this contract is to provide Enterprise-wide services and solutions for emerging technology including supporting new technology project implementation and transition to operations, Enterprise architecture and data science support, application development and management, IT related training, and support and training of interns in appropriate fields. This contract facilitates support to establish a “new technology pipeline”. Specific efforts include development and maintenance of custom applications and/or databases on a variety of platforms to include cloud, mobile, and containerized environment to meet network standards, in addition to the sustainment and upgrade of command legacy applications and information assurance. The responsibilities and tasks associated with each requirement play a pivotal role for the SIE and ultimately the end-user. The contractor shall provide project teams with the necessary skills to transition new capabilities into the SIE. The project team will plan, develop, test, install, operate, and maintain new capabilities, as required, before requesting USSOCOM approval for official release. Project status updates will be provided by the contractor. The project team shall produce required build documentation and training materials, as well as test the environment to ensure a smooth transition to the operations and maintenance team.

For all projects the contractor will implement a project control system that will assist in effective management of all schedule and work elements of the program. This system must provide accurate and rapid insight into the contractor’s milestones, performance, areas of difficulty and their impact, and schedule adjustment.

The contractor will provide elevated Tier technical customer support for all developed applications and projects as needed or requested by the Government. Coordinate resolution of elevated trouble tickets and when required submit escalated functional problems.

The objectives highlight a combination of enduring and non-enduring support to meet the Enterprise Development, Application and Training needs.

General Objectives:

1. Program Management

2. Emerging Solutions

3. Technology Solutions Support

4. Application Development and Management

5. Training

6. Internship/Fellowship Program Management The Contractor shall provide management support for this contract to include the management and oversight of all activities performed by contractor personnel, including subcontractors, to satisfy the requirements identified in this SOO and the TO Performance Work Statements.

Coordinate a Contract Kick-Off Meeting The contractor shall schedule, and coordinate a Kick-off Meeting (Section 5.3, Table 3, D-002) at a location approved by the Government. The meeting shall provide an introduction between the contractor and Government personnel involved with the contract. The meeting shall provide the opportunity to discuss technical, management, security issues, travel authorization, and reporting procedures. At a minimum, the attendees shall include Key contract Personnel, COR(s), General Services Administration (GSA) Contracting Officer (CO) and other relevant Government personnel.

The Contractor shall provide a meeting agenda at least five working days prior to the Kick-off Meeting (Section 5.3, Table 3, D-003)

The Contractor shall provide the following at least working three days prior to the Kick-off Meeting:

Copy of the Contract Transition-In Plan (Section 5.3, Table 3, D-009) Draft Contract Program Management plan (Section 3.5, Table 3, D-001) Draft Quality Management Plan (QMP, Section 5.3, Table 3, D-006) Organizational chart identifying Company Owner/President/Project Manager (PM)/Contract Manager/Financial Officer and other key personnel contact information.

Draft Contract Implementation Plan for review (Section 5.3, Table 3, D-005) The Contractor shall provide a meeting minutes no later than five days after the Kick-off Meeting (Section 5.3, Table 3, D-004) Prepare a Monthly Status Report (MSR) The Contractor shall develop and provide an MSR (Section 5.3, Table 3, D-011). The MSR shall include the following:

Activities during the reporting period, by task order and task (include ongoing activities, new activities, activities completed, and progress to date on all above-mentioned activities). Each section shall start with a brief description of the task order and task.

Problems and corrective actions taken. Also, include issues or concerns and proposed resolutions to address them.

Personnel gains, losses, and status (security clearance, etc.).

Government actions required.

Schedule (show major tasks, milestones, and deliverables, including planned and actual start and completion dates for each).

Summary of trips taken, conferences attended, etc. (attach Trip Reports to the MSR for the reporting period).

Accumulated invoiced cost for each contract line-item number (CLIN) up to the previous month.

Projected cost of each CLIN, including SubCLINs, for the current month.

Program Management Review (PMR) Meeting The Contractor shall convene a quarterly PMR with the COR and other Government stakeholders. The purpose of this meeting is to ensure all stakeholders are informed of the monthly activities and the Monthly Status Report (MSR), to provide opportunities to identify other activities and establish priorities, and to coordinate resolution of identified problems or opportunities. The contractor shall submit project reviews quarterly describing the status of all projects and financial information using Government provided template.

Within five working days (Section 5.3, Table 3, D-012) of the conclusion of the Quarterly PMR, the Contractor shall provide meeting minutes to include, but not limited to, the list of attendees, issues discussed, decisions made, and action items assigned.

Prepare and Update a Contract Program Management Plan (CPMP) The contractor shall document all support requirements in a CPMP and provide it to the Government (Section 5.3, Table 3, D-001).

The CPMP shall:

Describe the proposed management approach.

Contain detailed Standard Operating Procedures (SOPs) for all tasks.

Include milestones, tasks, and subtasks required in this contract.

Describe in detail the contractor’s approach to risk management.

Describe in detail the contractor’s approach to communications, including processes, procedures, format, and other rules of engagement between the contractor and the Government.

Include the contractor’s QMP.

The CPMP is an evolutionary document that shall be updated annually at a minimum and as changes occur. The contractor shall work from the latest Government-approved version of the CPMP.

Transition The contractor shall execute a transition plan to minimize interruptions or delays to work in progress that would impact the mission.

a. Transition-In The contractor shall provide within 14 calendar days of contract award a Transition-In Plan in accordance with Section 5.3, Table 3, D-009.

The contractor shall ensure that there will be minimum service disruption to vital Government business and no service degradation during and after transition. The contractor shall conduct a transition-in mid-point assessment meeting to update the Government on the status of the transition.

b. Transition-Out The contractor shall provide a Transition-Out Plan 90 calendar days, or more, prior to the end of the period of performance in accordance with Section 5.3 Table 3, D-010.

The Transition-Out Plan shall facilitate a seamless transition from the incumbent to the incoming contractor or Government personnel at the expiration of the contract. The contractor shall provide a Transition-Out Plan no later than 90 calendar days and implement the plan no later than 60 calendar days prior to the expiration of the contract.

The contractor shall identify how it will coordinate the transfer of institutional knowledge gained through the performance of the TO with the Government to include, but not limited to, the following:

1. Program management processes.

d. Points of contact.

e. Location of technical and program management documentation/processes.

f. Status of ongoing initiatives.

g. Appropriate contractor-to-contractor coordination to ensure a seamless transition.

h. Transition of Key Personnel.

i. Actions required of the Government.

The contractor shall also establish and maintain effective communication with the incoming contractor and Government personnel for the period of the transition via daily status meetings.

Contract Implementation Plan The contractor shall provide a Contract Implementation Plan (SOO Section 5.3, D-005) to a designated repository within 30 calendar days of contract award that breaks down the strategic plan for contract execution into smaller steps that define the timeline, the personnel/teams and the resources that will be needed.

System Security Plans The contractor shall submit System Security Plans (SOO Section 5.3, D-007) to a designated repository within 30 calendar days of contract award. The plans shall address the processes and methodologies involved with keeping information confidential, available, and assuring its integrity. The plan shall also address access controls, which prevent unauthorized personnel from entering or accessing a system; protecting information no matter where that information is, i.e., in transit (such as in an email) or in a storage area and the detection and remediation of security breaches, as well as documentation those events.

Corrective Action Plans The contractor shall provide corrective action plans (CAPs, SOO Section 5.3, D-008) as requested by the Government. Plans are due within 10 working days of Government request. These CAPs will be targeted outcomes for the resolution of undesirable actions/performance. The CAPs record what participating parties should do to correct undesirable contractor actions. CAPs updates shall be provided to the Government as required and closed upon Government approval.

Quality Management Plan The contractor shall ensure all work will be performed in accordance with the contract requirements, in compliance with the FAR clause 52.212-4, paragraph entitled “Inspection/Acceptance.” The contractor shall maintain and submit to the Government, within 30 days after award, a complete Quality Management Plan (QMP; SOO, Section 5.3, Table 3, D-006) addressing the inspection system used to ensure the requirements of this contract are met. The contracting officer shall notify the contractor of acceptance or any required modifications. The QMP shall include the following minimum requirements:

A description of the inspection system to cover all major services and deliverables. The description shall include specifics as to the areas to be inspected on both a scheduled and unscheduled basis, the frequency of inspections, and the title of inspectors.

A description of the methods to be used for identifying and preventing defects in the quality of service performed.

A description of the records to be kept to document inspections and corrective or preventative actions taken.

All records of inspections performed shall be retained and made available to the Government upon request throughout the contract performance period, and for the period after contract completion, until the final settlement of any claims under this contract.

Records Management Contractor services may require management of Federal records. If the contractor holds Federal records, the contractor must manage Federal records in accordance with all applicable records management laws and regulations, including but not limited to the Federal Records Act (44 U.S.C. chs. 21, 29, 31, 33), and regulations of the National Archives and Records Administration (NARA) at 36 CFR Chapter XII Subchapter B). Managing the records includes, but is not limited to, secure storage, retrievability, and proper disposition of all federal records including transfer of permanently valuable records to NARA in a format and manner acceptable to NARA at the time of transfer. The agency also remains responsible under the laws and regulations cited above for ensuring that applicable records management laws and regulations are complied with through the life and termination of the contract.

Emerging Solutions Emerging Solutions requirements will be Non-Enduring Support and projects will be defined at the TO level. The contractor will integrate and deliver an indefinite quantity of platforms created to identify and transition emerging capabilities to support strategic objectives of the Command (mission enhancement, modernization, etc.). The project concepts are intended to be a SOF Enterprise Architecture Innovation effort. The intent is to create a dynamic and stimulating environment to collaborate and engage multi-partner participation (multi-agency, industry, academia and non-traditional) on capturing full spectrum data coverage, and provide support and troubleshooting necessary to transition emerging solutions from pilot to Enterprise scale for full implementation of approved projects.

Technology Solutions Support Technology Solutions requirements will be Enduring Support and defined as key integrators for solutions across the SIE, and incorporate labor support (e.g. Enterprise Architects (EA), Data Science, etc.). The contractor will integrate and deliver an indefinite quantity of research, design, and development of Enterprise Architecture products, primarily using the DoD Architecture Framework (DoDAF). Contractors performing USSOCOM EA tasks shall provide overall DoDAF, Joint Capabilities Integration and Development Systems (JCIDS) and SOF Capabilities Integration and Development Systems (SOFCIDS) situational awareness to the Enterprise, will understand USSOCOM strategies, missions, roles, and functions, and perform mid- and long-term Enterprise and strategic C4 planning based on this understanding. They will understand and use the DoDAF, JCIDS, SOFCIDS, and other key DoD/Joint architecture planning instructions to create and maintain the EA using DoDAF architecture products and supporting documentation. The contractor shall create the EA and capability architectures as described at the TO level and integrate and deliver an indefinite quantity of support to develop and assist in Big Data, data handing, data processing and issues across the SIE. The contractor will support Development Security Operations in new developments, specifically regarding the SIE Cloud efforts. The contractor shall provide support following the guidance of the specific at the TO level.

Application Development and Management Application Development and Management will be Enduring Support and will incorporate labor support. The contractor will integrate and deliver an indefinite quantity of enduring support to develop, administer, implement, and maintain custom developed applications/databases for the SIE spanning multiple systems and networks. Solutions must be developed in full accordance with DoD and organization regulations, directives, and customer procedures, and the specific guidance at the TO level.

The contractor shall develop, document, and sustain new applications on a variety of platforms to include cloud and mobile. They will maintain, sustain and upgrade legacy applications and containerize legacy applications to meet the network standards as required. The contractor will develop/transition containerized software applications to enhance the security posture of the network, provide operation and maintenance support of current and legacy applications, and provide database development and sustainment.

Training Training will be Non-Enduring support and projects will be defined at the TO level. The contractor will integrate and deliver an indefinite quantity of products and support for training. The contractor shall create, update and maintain training capabilities for communications, IT, support and end-user personnel. The contractor shall support course curriculum and training efforts across the SIE through USSOCOM locations including local, remote and mobile training specified by the Government. Classes shall be developed and instructed on topics specified in the PRD.

Internship/Fellowship The contractor will integrate and deliver an indefinite enduring quantity of products and support for internship and fellowship. As part of the Artificial Intelligence (AI)-ready workforce and AI outreach lines of effort academic, DoD, and federal agency internship/fellows programs may be sponsored as part of the talent acquisition process. Special Projects will be solicited from across the SOF Enterprise, projects selected which can benefit the SOF Enterprise will be allocated Interns/Fellows to work with Military/GS Civilian/contractors to create unique solutions to SOF problems.

Contract Management Contract Type The contract type will be structured as an IDIQ.

Period of Performance The period of performance for this contract will be 1 August 2023 – 31 July 2024.

Contract Line Item Numbers (CLIN) The CLIN structure will be defined at the TO level.

Place of Performance All support provided by the contractor under this contract shall be performed onsite within facilities provided by USSOCOM, its Component Commands, TSOCs, and deployed forces or other Government-provided or designated facilities, unless otherwise agreed upon by the COR and/or the KO. The COR and KO may authorize performance at offsite locations, to include regular/reoccurring telework. The contractor shall provide global support 24 hours a day, 7 days a week, over the period of performance of the contract unless otherwise stated in the PRD or approved in advance by the COR at the given work location.

Regular/Reoccurring Telework The Government is under no obligation for maintenance, insurance, or other fiscal costs associated with telecommunication services.

In the event of IT issues, the Government will not be charged for time troubleshooting or on the phone with help desk support. If the issue cannot be resolved via remote access, the contractor shall transport the computer/kit to the designated Government location for repair and will work at the Government site until computer/kit issues are resolved.

Regular and reoccurring telework is dependent upon continued satisfactory performance and is at the discretion of Government and may be revoked.

In the event that telework status is revoked, or employment is terminated, the contractor agrees to return all Government furnished equipment (GFE) to the Government.

Other Locations The Government shall provide guidance, direction, and/or approval instructions as to the virtual/remote/teleworking environments going forward to ensure that the contractor shall have the required equipment, software, infrastructures and all other applicable opportunities in place upon contract execution.

Work Hours The contractor shall provide its support during the duty hours at each assigned work location unless otherwise stated in this contract or approved in advance by the KO or the COR at a given work location.

Federal Holiday Observance The following United States (US) Federal Holidays in Table 2 are recognized, and the contractor is not required to work on these dates, unless otherwise specified in individual taskings:

TABLE – 2 Observed Holidays

Any other day not listed above that is designated by Federal Statute, Executive order, or the President’s proclamation.

Holiday Access On‐site personnel assigned to this contract shall not be granted access to the installation during the holidays in Section 6.3., except as follows: the contractor shall provide sufficient on‐site personnel to perform round‐the‐clock requirements of critical work already in process unless otherwise instructed by the CO or authorized representative. If the contractor's on‐site personnel work during a holiday other than those in paragraph Section 6.3, no form of holiday or other premium compensation shall be reimbursed as either a direct or indirect cost.

ITMO Tools The contractor shall use the ITMO portal and tools to manage contract information. All applications created by the ITMO shall be used for contract management as dictated by the Government.

These tools were created for contract management to improve customer service by the Special Operations Forces Information Technology Enterprise Contract management team as a system of record for tracking important contract information including but not limited to the ability to manage contracts, personnel (staff), contractors, users, position descriptions, billets, travel, overtime, telework, CDRL delivery, contract assessment and delivery, and reports. The vendor will be expected to purchase computer(s) on the USSOCOM Approved Hardware List to support back-office access to the ITMO tools.

Contractor Interactions The SIE includes the personnel, equipment, advanced technologies, and processes that, in concert with our Joint Forces, Interagency and Multinational partners, sustains our national defense mission. Operating, maintaining, upgrading, and keeping the SIE innovative and current with new technology requires efforts from multiple contractors and Government organizations. The SIE mission is paramount. Contractors will be co-located with other contracting companies providing IT services to USSOCOM and must interact with the mission as the priority at all times. Contractors will engage with one another fairly, cooperatively, and professionally at all times. Contracting companies will minimize active recruiting from other servicing vendors. Recruitment outside of existing USSOCOM employee pools is encouraged.

Personnel Key Personnel Key Personnel shall be proposed by the vendor and negotiated with and approved by the Government. The Government expects approximately five Key Personnel and Program Management will be represented at the TO level.

Staffing Tool The contractor shall use the Personnel, Equipment Tracking Application (PETA) or any other Government developed tool that supersedes PETA and supports contract management.

PETA was created for contract management to improve customer service by the Special Operations Forces Information Technology Enterprise Contract management team as a system of record for personnel staffing and equipment tracking. The application provides the ability to manage contracts, personnel (staff), contractors, users, position descriptions, billets and reports.

Quality Assurance Surveillance The contractor must ensure a standard of quality is executed based on the requirements established in the contract and the TOs. The purpose of the quality assurance surveillance is to monitor quality levels based on the requirements listed in the SOO and TO level. The surveillance is set forth based on the procedures and guidelines of USSOCOM to ensure the required quality objectives/standards are achieved by the contractor. The Government will reinforce the quality standards by implementing a Quality Assurance Surveillance Plan (QASP) enforcing the standard expectations. The USSOCOM EDAT QASP will be used to evaluate performance of the contract and all of its’ TOs. Both contract performance and TO level performance requirements specific for each TO will be evaluated monthly and annually with the Monthly Quality Assessments (MQAs) and Annual Quality Assessments (AQAs). MQAs may be evaluated by TO, CLIN or SLIN as appropriate.

Deliverables Inspection of contractor performance shall take place on-site by the Government (e.g., by customer and the COR). Inspection and acceptance of all deliverables under this contract will be performed by the COR.

Scope of Inspection All deliverables will be inspected for content, completeness, accuracy, and conformance to contract requirements by the COR. The contractor will abide by the established contract performance factor identified on contract. The contractor will be responsible to maintain the designated management tools and delivery submissions identified by the COR. Inspection may include validation of information or software using automated tools, testing, or inspections of the deliverables, as specified in the contract. The scope and nature of this inspection will be sufficiently comprehensive to ensure the completeness, quality, and adequacy of all deliverables.

The Government requires a period not to exceed 15 workdays (unless specified otherwise) after receipt of deliverable items for inspection and acceptance or rejection.

Contractor Responsibilities Provide all deliverables with complete, accurate content conforming to the contract requirements.

Abide by established contract performance factors.

Maintain designated management tools and delivery submission identified by the COR.

Provide an inspection period NTE 15 workdays for Government response.

Basis of Acceptance The basis for acceptance shall be compliant with the requirements set forth in the contract and relevant terms and conditions of the contract. The KO or COR will provide written notification of acceptance or rejection of all deliverables within 15 workdays (unless specified otherwise). All notifications of rejection will be accompanied with an explanation of the specific deficiencies causing the rejection.

If the Government finds that a deliverable contains spelling errors, grammatical errors, or improper format, or otherwise does not conform to standard English grammar, usage, punctuation, and spelling, the document may be rejected without further review and returned to the contractor for correction and resubmission. Upon receipt of the Government comments, the contractor shall have 10 (unless specified otherwise) workdays to incorporate the Government’s comments and change requests and to resubmit the deliverable. If the contractor requires additional Government guidance to produce an acceptable version, the contractor shall arrange a meeting with the COR. Acceptance will occur when all discrepancies, errors, or other deficiencies identified in writing by the Government have been resolved, through documentation updates, program correction, or other mutually agreeable methods.

Contractor Responsibilities Correct and resubmit rejected deliverables.

Incorporate comments and change requests within 10 workdays and resubmit.

Request review meetings with the COR for guidance as needed.

Contract Data Requirements List (CDRL) The CDRLs listed and described in Table 3 are required for this effort. The Government will provide the contractor with a deliverable format, if required.

At the request of the Government, Contractor input and exchange with the Government will be expected to iteratively draft and improve deliverables. Collaboration will improve understanding, manage expectations, and improve the product and the process. Additional CDRLs may apply to individual TOs or projects.

CDRLs one through 11 apply to the contract. CDRLs 13 through 35 are anticipated to apply to some or all TOs.

Table 3. Contract Data Requirements List (CDRL)

The report shall provide the following information broken out by TO:

· Significant accomplishments

· Planned activities for the coming month (and beyond)

· Problems and corrective actions taken. Also include issues or concerns and proposed resolutions to address them.

· Status report for all components of the Contract with discussion of any metrics that are not meeting the standard for a satisfactory rating to include an outline of any issues and a plan to return to satisfactory.

· Personnel gains, losses, and status (e.g., security clearance, etc.)

· Government actions required

· Summary of trips taken, conferences attended, etc.

· Financial summary (ceiling, funded, invoiced and Estimate at Completion (EAC)) for each CLIN and SCLIN up to the previous month to include travel and ODCs, if any

One time per TO, revisions as required

The contractor shall document all support requirements in a PMP. To include:

a. Detailed description of the proposed management approach.

b. Draft SOPs for all tasks.

c. Detailed milestones, tasks, and subtasks required in this TO.

d. Detailed description of the contractor’s approach to risk management under this TO.

e. Detailed description of the contractor’s approach to communications, including processes, procedures, format, and other rules of engagement between the contractor and the Government.

f. Description of how this TO integrates into the contractor’s QAP.

One time per TO; due at Project Kick-Off Meeting; revisions as project changes occur, no less frequently than annually