Creates a MyCC account with the associated structure.

VALIDATION

This endpoint handles the setup for all testing cases. There is parameter validation in place to avoid conflicting configuration choices.

• Onboarding enabled account cannot have more than 3 lanes.
• For upload log based data integration, there has to be at least 1 lane with a timestamp 3 months in the past.
• Each lane must have an installation timestamp
• Non 'Command Alkon' lanes cannot have lynx timestamps.
• The installed timestamp for lynx, when set, needs to be before the last file received timestamp.
• Lanes with production data must have a timestamp at least 4 months in the past.
• A mix design's compressive strength must be greater than 0 or null.
• For any given mix design, the design strength must be defined unless the QC scenario is NoData
• For any given mix design, the mix must have a baseline when the QC scenario is Sufficient.

FUNCTIONALITY

Insights

• Can create a myCC account with an arbitrary number of lanes, each with an installation timestamp less than 6 months ago or older than 7 months ago.
• By the setting the ExceededProductionGoal production data scenario, the corresponding lane has data available for more than 1 month.
• For any of the production scenarios, except for NoData, lanes have data available in the Insights report.
• For any of the production scenarios, except for NoData, there is data available in the Environmental report.
• For any of the production scenarios, except for NoData, there is daily summary data available.
• A lane using the Lagging scenario, is returned by the /Accounts/{myCCId}/Lanes/Lagging
• A lane using ExceededProductionGoal will be marked as ExceedingProductionGoal by the /Accounts/{myCCId}/Lanes/RecentProduction endpoint.
• A lane using the Lagging scenario is marked as not ExceedingProductionGoal by the /Accounts/{myCCId}/Lanes/RecentProduction endpoint.
• A lane using the SuggestionActions scenario is returned by the /Accounts/{myCCId}/Lanes/SuggestedActions endpoint.
• For any of the production scenarios, except for NoData the production report will be populated with the lane's injections.

MyData

• Lanes with a Command batching software are eligible for lynx.
• Lanes with a lynx installation timestamp are considered installed.
• Lanes without a Command batching software are not considered eligible.
• For eligible lanes, a lynx installation package can be downloaded. Note: The zip is fake, and does not actually generate the api key, configuration file, etc.

Batching Data

• Accounts can be created with a specified data integration type.
• The lynx data integration type can be set on a per lane basis, using the lynx timestamps.
• For the FileUpload data integration type, action items are available only when the IncludeError flag is set to true.
• When the LastLynxFileSeenTimestamp is set to more than 14 days in the past, the lynx batching table will show an error for this lane.

QcData

• For mix designs with the Limited qc data scenario, the there will be action items associated with them.
• Each qc data scenario directly corresponds to the mix design status in the /Accounts/{myCCId}/MyData/Qc/Table endpoint.

Mix Design Manager

• Each lane can be created with an arbitrary number of mix designs.
• For each, a mix strength can be specified.
• Each mix can be created with or without a baseline mix.
• Each mix can or cannot be user created.