Software Engineering Institute | Carnegie Mellon University

Contracting Officer Representatives (CORs)

The contract incorporates a DoD Sponsoring Agreement that establishes the mission, scope, and policy by which the Lab is operated and managed, consistent with FAR 35.017. The DoD Sponsoring Agreement details, and the USAF contract enforces, that projects operate with an agreement between CMU-SEI and the project customer (via the “Project Work Plan”). 

The project customer directly monitors their project and provides technical direction to CMU-SEI. For this reason, the USAF does not assign Contracting Officer Representatives (CORs) under this contract. Technical direction for individual projects is provided directly from Government customers to CMU-SEI staff; however, contractual direction is to be provided by the AFLCMC/AZS Procuring Contracting Officer (PCO) (overall contract administration is also provided by AFLCMC/AZS). Contractual direction includes concerns about allowable cost, funding, or issues surrounding non-performance of CDRLs. 

  Please contact the AFLCMC/AZS PCO and/or Contract Specialist for any contractual concerns.

DoD R&D New Starts

A new start program for RDT&E is a new program element or project, or a major component thereof, as determined by specific supporting information provided in the R-2 and R2A (RDT&E Budget Item/Project Justification) exhibits, not previously justified by the Department and funded by the Congress through the normal budget process.

It is incumbent on the customer to ensure that both the DoD rules and their own agency specific rules for New Starts are adhered to prior to sending funds to AFLMC/AZS.

RDT&E

Research, Development, Test and Evaluation (RDT&E) is one of the five major appropriations used by the Department of Defense. RDT&E finances research, development, test and evaluation efforts performed by both contractors and government installations in the developing equipment, material, or computer application software. This includes services (including government civilian salaries), equipment, components, materials, end items and weapons used in such efforts.

Severable vs Non-Severable

  This designation is important as it determines period of performance limitations consistent with fiscal law. Each determination will be made on a case-by-case basis.

Severable

A project is considered severable if the research services provided by CMU-SEI are continuing and recurring in nature and provide the Government a benefit each time the service is performed (ex.: ongoing/recurring software maintenance or monitoring). If your PWP includes terms such as “maintain”, “operate”, or “assist”, these are terms generally associated with severable services.

The period of performance will depend on the appropriation source, i.e. the “Color of Money” and year of the appropriation.

Customers should verify with their agency Financial Manager/Budget Specialist if they are unsure as to period of performance restrictions based on the appropriation.

Non-Severable

A project is considered non-severable if the research represents a single undertaking with a defined end-product that cannot feasibly be subdivided for separate performance (ex.: researching a new technology to determine if it is feasible, and delivering the results to the customer). There is no limitation on PoP for non-severable projects.